Offline content distribution networks

ABSTRACT

Approaches, techniques, and mechanisms are disclosed for the secure distribution of media content to devices having minimal or no Internet connectivity. Computing devices referred to herein as “local servers” are strategically deployed at various locations, such as stores and other public locations. Packages of media contents are stored on the local servers, and may be updated using various online and/or offline data transfer techniques. Portable devices may directly connect to the local servers via various types of proximity-based connections, such as by wireless local area networks, by wired connections over Universal Serial Bus cables, or by sharing of removable media such as Secure Digital cards. The local servers may copy their media contents to authorized devices when such connections are established. The contents on a device may be automatically be updated the next time the device connects to one of the local servers, so as to include newly selected and/or available content.

PRIORITY CLAIM

This application claims benefit under 35 U.S.C. §120 as a Continuationof U.S. application Ser. No. 14/878,360, filed Oct. 8, 2015, whichclaims benefit under 35 U.S.C. §120 as a Continuation of U.S.application Ser. No. 14/600,003, filed Jan. 19, 2015, the entirecontents of each of which is hereby incorporated by reference as iffully set forth herein. The applicant(s) hereby rescind any disclaimerof claim scope in the parent application(s) or the prosecution historythereof and advise the USPTO that the claims in this application may bebroader than any claim in the parent application(s).

TECHNICAL FIELD

Embodiments relate generally to distribution of media content, and, morespecifically, to techniques for distributing media content in areas withminimal data network connectivity.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

A variety of systems and techniques exist for distributing media contentto media playback devices. Media playback devices may include, withoutlimitation, mobile phones, tablets, laptop or desktop computers, set-topboxes, and other consumer electronic devices. Many existing systems andtechniques rely upon media playback devices that have nearly ubiquitousaccess to a network, such as a cellular phone network, the Internet,and/or a cable network, over which the media content is distributed. Amedia distributor will typically have a large catalog of available mediacontent stored on one or more media distribution servers that aredeployed at various locations within the network. The catalog willtypically be much larger in storage size than the media playback devicesare capable of storing. Hence, the servers will typically provideinterfaces by which a user may browse the catalog over the network usingvarious applications at media playback devices operated by the user.Users may select specific items of media content from the catalog, whichare then transferred over the network from the servers to the mediaplayback devices.

The media content may be viewed in a “streaming” manner, in that thereceiving media playback device is configured to begin playing the mediacontent while it is still receiving the media content. Or, the contentmay be stored at the media playback device for subsequent viewing atsome time after the content is downloaded. The network is furthermoretypically utilized for determining whether the media playback device isauthorized to play certain media content. For instance, a user may berequired to “log-in” to a media distribution server from time to time inorder to view content from the media distribution server. Or, the mediaplayback device may be configured to authenticate itself to the mediadistribution server before being allowed to play media content from themedia distribution server.

Media distribution techniques and systems such as described above workbest in geographic areas where media playback devices frequently havedirect access to the network at which the media distribution server(s)are deployed. However, in many parts of the world, such as in developingcountries, access to such networks may be limited and/or prohibitivelyexpensive. Consequently, many existing systems and techniques fordistributing media content in these parts of the world are deficient.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements and in which:

FIG. 1 is an illustrative view of various aspects of an example systemin which the techniques described herein may be practiced;

FIG. 2 illustrates an example process flow for distributing content tooffline client devices; and

FIG. 3 is block diagram of a computer system upon which embodiments ofthe invention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

Embodiments are described herein according to the following outline:

1.0. General Overview

2.0. Structural Overview

-   -   2.1. Central Content Distribution Server    -   2.2. Content Packages    -   2.3. Local Content Distribution Servers    -   2.4. Offline Client Devices    -   2.5. Client Applications    -   2.6. Digital Rights Management    -   2.7. Variations

3.0. Functional Overview

-   -   3.1. Local Content Server Deployment    -   3.2. Distribution of Content to Local content servers    -   3.3. Device Provisioning    -   3.4. Offline Transfer to Portable Devices    -   3.5. Rights Management and Payment    -   3.6. Miscellaneous

4.0. Example Embodiments

5.0. Implementation Mechanism—Hardware Overview

6.0. Extensions and Alternatives

1.0. General Overview

Approaches, techniques, and mechanisms are disclosed for the securedistribution of media content to devices having minimal or no Internetconnectivity. Computing devices referred to herein as “local servers”are strategically deployed at various locations, such as stores andother public locations, which may not necessarily have access to theInternet. Packages of media contents are stored on the local servers,and may be updated using various online and/or offline data transfertechniques. Portable devices may directly connect to the local serversvia various types of proximity-based connections, such as by wirelesslocal area networks, by wired connections over Universal Serial Bus(“USB”) cables, or by sharing of removable media such as Secure Digital(“SD”) cards. The local servers may copy their media contents toauthorized devices when such connections are established. The contentson a device may be automatically updated the next time the deviceconnects to one of the local servers, so as to include newly selectedand/or newly available content.

In an embodiment, a user may pay for his or her content using any of avariety of payment arrangements, including billing by a merchant onwhose premises a local server has been deployed, billing by a mobilenetwork service provider, or billing by the content distributor.Depending on the embodiment, access to the content may be purchased on asubscription basis, or ala carte for individual content items. In anembodiment, the content is protected using any suitable digital rightsmanagement scheme. Using minimal bandwidth, keys or codes for decryptingor unlocking content may quickly be distributed via a centralized serverto devices or local servers, once a devices' right to access the contenthas been verified. For devices and/or local servers that lack Internetaccess, transactions and/or provision of any necessary keys or codes maybe conducted via Short Message Service (“SMS”) messages.

In an embodiment, a device is provisioned for access to the contentdistribution system by a user or merchant installing an application onthe device. Then, the user or merchant may use the application toregister the device with the content distribution system. Paymentinformation may optionally be taken at the time of registration. Theinstalled application is used to decrypt, play, or otherwise allowaccess to content downloaded from a local server. The application mayfurthermore be responsible for automatically connecting to a localserver and downloading new content. In an embodiment, the applicationmay provide various interfaces for browsing content catalogs, selectingnew content, paying for new content, and/or sharing content or contentcatalogs with other devices.

In other aspects, the invention encompasses a computer apparatus and acomputer-readable medium configured to carry out the foregoing steps.

2.0. Structural Overview

FIG. 1 is an illustrative view of various aspects of an example system100 in which the techniques described herein may be practiced, accordingto an embodiment. System 100 comprises one or more computing devices.These one or more computing devices comprise any combination of hardwareand software configured to implement the various logical componentsdescribed herein, including components 110-190. For example, the one ormore computing devices may include one or more memories storinginstructions for implementing the various components described herein,one or more hardware processors configured to execute the instructionsstored in the one or more memories, and various data repositories in theone or more memories for storing data structures utilized andmanipulated by the various components.

2.1. Central Content Distribution Server

System 100 comprises one or more central content distribution servers110, also referred to herein as central servers 110. A central server110 is a set of one or more computer devices, coupled together by one ormore networks, that are collectively configured to provide variousfunctionality as described herein. The central server 110 will typicallybe operated for or on behalf of a content distributor.

Central server 110 includes or is connected to one or more datarepositories 112. Data repositories 112 store media content 114 that isretrievable by central server 110. Data repositories 112 may take any ofa variety of forms, such as file systems, databases, and so forth.Depending on the embodiment, media content 114 may include any of avariety of media content items, such as digital video files, digitalmusic files, installable computer game files or other softwareapplications, and so forth. Data repositories 112 further store metadata116, associated with the media content 114, that describe variousaspects of each individual item of media content. Example metadata 116may include content titles, descriptions, thumbnails, categorical data,digital rights management (“DRM”) data such as licensing constraints ordecryption keys, rendering information, content trailers, associatedadvertisements, and so forth.

Central server 110 may optionally be coupled to any number of onlineclient computing devices 130 via one or more wide area networks 190,such as the Internet. Online client computing devices 130 may include,for instance, mobile phones, personal computers, and/or any othersuitable computing devices. Central server 110 may be configured tocommunicate directly with web browsers and/or other applications on theonline client devices 130 to provide the online client devices 130 withaccess to items of media content 114 via any suitable content streamingor downloading technique.

2.2. Content Packages

In an embodiment, system 100 includes a content packaging component 120configured to generate content packages 124. Content packages 124 aredata structures that store groups of media content 114 and associatedmetadata 116 from data repository 112 in a common format. The exactformat of each content package 124 may vary depending on the embodiment,but may include, without limitation, a directory or other hierarchicalstructure, a compressed file, a database, and/or a table. Contentpackages 124 may include, for instance, a group of video clips,different versions of those clips for different device profiles,associated titles and descriptions, thumbnails, trailers,advertisements, and/or categorical data. Depending on the embodiment,different content packages 124 may or may not include a same item ofmedia content 114.

Content packaging component 120 may be implemented as an application orother set of computer processes running on central server 110, or on aseparate set of one or more computing devices that are communicativelycoupled to data repository 112. Content packaging component 120implements logic for retrieving a defined set of media content 114 andassociated metadata 116, and generating an appropriate content package124 based thereon. In an embodiment, content packaging component 120 isfurther configured to store copies of a given content package 124 ondifferent removable media, such as the USB memory stick as depicted inFIG. 1. In an embodiment, content packaging component 120 may further orinstead be configured to send content packages 124 to various devicesover one or more networks, such as Internet 190.

Content packaging component 120 may further implement logic for definingthe group of items of media content 114 that are to be included in agiven content package 124. This logic may, in some embodiments, be atleast partially automated. For instance, content packages 124 may beformed based on various items of metadata 116, such as release dates,studios, genres, series, and/or any other suitable metadata 116. Thelogic for defining groups may also or instead comprise logic forgenerating user interfaces and receiving, via those interfaces, userinput from a human operator that selects media items to include in agroup.

2.3. Local Content Distribution Servers

System 100 further comprises local content distribution servers 150,which are also referred to herein as local servers 150. Local servers150 are stand-alone computing devices. In an embodiment, local servers150 are deployed strategically in various public or semi-publiclocations, such as in mobile phone stores, coffee shops, video stores,grocery stores, train stations, busses, airplanes, airports, and soforth. A local server may be, without limitation, a desktop computer, alaptop, a kiosk, a mobile phone, a headless computing appliance, or anyother suitable type of computing device. A local server 150 may furtherinclude various peripheral devices, such as USB hubs, network switches,routers, and so forth. A local server 150 may execute a variety ofcomputer processes configured to implement various functionalitiesdescribed herein. For instance, a local server 150 may execute, withoutlimitation, a web server, file server, web application(s), communicationrouting logic, and so forth.

Promoting Entities

In many embodiments, a local server 150 will be deployed on the premisesof some promoting entity. The promoting entity may have requesteddeployment of the local server 150 or otherwise agreed to the deploymentfor varying reasons. For instance, a promoting entity may perceive thedeployment as a potential source of additional foot traffic to thepromoting entity's store. As another example, a promoting entity may becompensated using various compensation structures, such as a flat feearrangement or a commission on content sales. A promoting entity mayalso, in some embodiments, support the content distribution process byprovisioning client devices 160, accepting payment, updating the localserver 150 or contents stored thereon, and so forth.

Local Connections

Local servers 150 comprise one or more local networking components 158.The one or more local networking components 158 are configured toestablish communication links to offline client devices 160 for variouspurposes described herein. The communication links are such that theyare only established when devices 160 are within a certain geographicproximity of a local server 150 (e.g. within a wireless transmissionrange of antennas attached to the local server 150, or only whenconnected directly by a cable to the local server 150). Thecommunication link between a local server 150 and an offline clientdevice 160 is described herein as a “local” connection. One example of alocal connection is a wired or wireless local area network connection(in contrast to a wide area network connection such as a connection toInternet 190). Another example of a local connection is a peer-to-peerconnection, such as a USB connection or an ad hoc wireless connection.In an embodiment, the communication link between a local server 150 andan offline client device 160 is a direct communication link, in thatcommunications do not pass through intermediary devices such as routersor gateways outside of the local server 150. However, in otherembodiments, the communication link does not necessarily need to bedirect.

The links may be of any suitable connection type, including wired and/orwireless connections, and communications may be conducted using anysuitable protocol. For instance, a local server 150 may include one ormore wireless access points for communicating with clients 160 usingvarious 802.11 protocols. As another example, a local server 150 mayinclude one or more Bluetooth adapters for communicating with clients160 via the Bluetooth protocol. As yet another example, a local server150 may include various ports by which wired connections may beestablished with clients 160, such as Universal Serial Bus (“USB”)ports, Ethernet ports, and so forth.

Offline Servers

Notwithstanding their ability to communicate with clients 160, localservers 150 may nonetheless be “offline” components of system 100, inthat in many embodiments local servers 150 are configured to provide thefunctionalities described herein without necessarily beingcommunicatively coupled to central server 110 or content packagingcomponent 120. In some embodiments, local servers 150 do not have accessto any network by which the local servers 150 can communicate withcentral server 110 and/or content packaging component 120. For instance,local servers 150 may be deployed in remote areas where Internet accessis unavailable.

In other embodiments, some or all of local servers 150 may be configuredto establish one or more communication links by which they maycommunicate with central server 110 and/or content packaging component120. A suitable communication link to central server 110 may beestablished using any suitable component, including without limitation aDSL modem, a cable modem, a 3G or 4G cellular-based modem, a dial-upmodem, and so forth. In many such embodiments, however, thecommunication link(s) will be of relatively low bandwidth and/orrelatively expensive to establish, such that the communication link(s)are impractical for use by offline client devices 160 to stream ordownload media contents 114 from central server 120. For instance, localservers 150 may only have sporadic access to the Internet, or haveaccess to the Internet via a service provider that imposes constraintson the amount of data that the local servers 150 may download over agiven period of time.

Content Storage

Local servers 150 further comprise one or more local storage devices152. The one or more storage devices 152 are configured to store localmedia content 154, which are subsets of the media contents 114 andmetadata 116 found in data repository 112. In an embodiment, the localmedia content 154 is organized as a set of one or more content packages124. In an embodiment, a high-speed storage media, such as a flash driveor RAID array, may be utilized for the one or more storage devices 152,so as to ensure that media content 154 may be quickly retrieved anddelivered to multiple client devices 160 at a time. However, in otherembodiments, any suitable storage mechanism may be utilized.

In an embodiment, a local server 150 may further comprise one or moreremovable storage drives by which the local server 150 may read and/orwrite to removable non-volatile computer-readable media, such as SecureDigital (“SD”) cards or USB storage devices. In an embodiment, theremovable media may, in turn, be inserted into or otherwise read byclient devices 160.

In an embodiment, the removable media storage drives may further orinstead be utilized to read and copy new local media content 154 to theone or more storage devices 152. For instance, content packagingcomponent 120 may be configured to write content packages 124 to SDcards or USB drives which are then transported by mail or other suitablecarrier to operators of local servers 150. The content packages 124 maythen be copied from the SD cards or USB drives to the local servers 150.The removable media may be disposable, shared with other local servers150, or returned to the operator of the content packaging tool 120 fordelivery of updated or new content packages 124 in the future. Inembodiments without a content packaging component 120, various items ofmedia content 114 and metadata 116 may be copied to removable mediadirectly from central server 110.

In an embodiment, the one or more local storage devices 152 may actuallyinclude removable storage devices. For instance, an operator of contentpackaging component 120 may copy a content package 124 to a USB driveand deliver the USB drive to an operator of a local server 150. The USBdrive is plugged into the local server 150, and then utilized as one ofthe one or more storage devices 152 until such time that the contentpackages 124 stored thereon are deemed out-of-date.

In an embodiment, a portable computing device may take the place of aremovable storage device. For instance, copies of content packages 124may be stored on a smartphone, which is configured to upload the contentpackages to a local server 150 via a wired or wireless communicationlink. In an embodiment, the smartphone may be configured to do soautomatically when a connection to a local server 150 is detected (e.g.when plugged into the USB port of the local server 150, or when withinproximity of a wireless access point of the local server 150).

In an embodiment where local server 150 has an at least intermittentconnection to central server 110, a local server 150 may instead beconfigured to download some or all of local media content 154 directlyfrom central server 110.

2.4. Offline Client Devices

System 100 further comprises offline client devices 160. Offline clientdevices 160, which are at times referred to herein as clients 160 ordevices 160, are portable computing devices such as traditional mobilephones, smart phones, gaming devices, portable media players, tablets,laptop computers, and so forth. Devices 160 are termed “offline”devices, in that, via interactions with local server 150, they arecapable of playing media contents 114 without necessarily beingcommunicatively coupled to central server 110.

In an embodiment, some or all of devices 160 are deployed in system 100in such a manner that they are incapable of accessing central server110. For instance, devices 160 may be deployed in remote areas whereInternet access is unavailable, unreliable, cost-prohibitive, etc. Or,devices 160 may not comprise suitable networking components foraccessing the Internet. In an embodiment, some or all of devices 160 aredeployed in system 100 in such a manner that the streaming ordownloading of media content 114 from central server 110 is impracticalor undesirable. For instance, devices 160 may have relatively lowbandwidth Internet connections and/or metered Internet connections thatare relatively expensive to maintain.

In some embodiments, a given device may be both an offline device 160and an online device 130, depending on when, where, and/or how it isused. For instance, a smartphone used in a remote area without cellulardata services may function as an offline device 160, whereas the samesmartphone, if used in a metropolitan area, might function as an onlinedevice 130.

Instead of downloading or streaming media content 114 from centralserver 110, devices 160 are configured to stream or download the localcopies 154 of media content 114 from local servers 150. Devices 160 maydo so automatically when a connection to a local server 150 isestablished, or at the request of a user. Thus, for instance, a user maybring a portable device 160 into a store where a local server 150 isdeployed. The portable device 160 may automatically (or at the requestof the user) download specific items of media content 114 of interestwhile the user is shopping at the store.

A device 160 may further be configured to automatically download certainmetadata 116 from a location on the content server 150. The retrievedmetadata 116 may describe media content 154 that is available on thelocal server 150, and/or other items of media content 114. The device160 may then present a user interface that shows the available contentto a user and allows the user to select which content to download. Forinstance, the device 160 may present a catalog of content, from whichthe user may select specific items to download. Or, the user may selectcharacteristics of content that the user would like to automaticallydownload (e.g. by date, genre, actor, studio, subscription package,etc.). The device 160 then downloads any selected content from a localserver 150.

Metadata 116 may be downloaded while the device 160 is connected to alocal server 150, and then stored for use while the device 160 is notconnected to any local server 150. In some embodiments, metadata 116 mayoptionally be downloaded directly from central server 110. The device160 may present various navigable interfaces for browsing metadata 116while not connected to a local server 150, and store a record of mediacontent items specifically selected by a user and/or in which a userexpressed interest. The next time the device 160 is connected to a localserver 150 that stores a selected content item or item of interest, thedevice 160 may automatically download the content item.

A single device 160 may be connected to different local servers 150 atdifferent times and in different locations. Different local servers 150may provide the device 160 with access to different subsets of items inmedia content 114, or local servers 150 may provide access to the samesubsets of items, depending on the embodiment. In an embodiment, once adevice 160 has been configured to automatically connect to and downloadcontent from one local server 150, the device 160 is capable ofautomatically connecting to and downloading content from other localservers 150 to which the device 160 has never connected.

For instance, each of the local servers 150 may be configured to use acommon local address for initiating communications with a device 160.The first time a device 160 connects to any local server 150 in system100, the device 160 will be configured (e.g. via installing anapplication or other suitable set of instructions) to automatically senda message to the common local address upon connecting to certain typesof networks (e.g. a network having a certain ssid or othercharacteristics). Then, when a device 160 connects to those types ofnetworks, the device 160 will automatically send a message to the localaddress, announcing the presence of device 160. The local server 150 maythen respond with information such as a catalog of contents 154 storedat the local server 150, requested items of content 154, and so forth.

However, in other embodiments, a device 160 may need to be separatelyprovisioned for each of at least some of the local servers 150.

2.5. Client Applications

In an embodiment, one or more special content access client applicationsare installed on devices 160. For instance, a web server on the localserver 150 may automatically direct a device 160 to an installer for acontent access application when a device 160 that lacks the applicationattempts to connect to the local server 150. Or, a process executing onthe server may automatically attempt to install the content accessapplication on the device 160 when the device 160 is plugged into thelocal server (e.g. via a USB connection). As yet another example, aninstaller for the client access application may be executed by thedevice 160 from a removable storage device such as an SD card. Dependingon the embodiment, the installation process may be initiated and/orconducted by the user of the device or an owner or operator of the localserver 150.

Generally, a content access client application (also referred to hereinas a “client application”) is at least responsible for allowing thedevice 160 to play items of content 154 downloaded to the device 160.For instance, the client application may be or comprise media playbacksoftware. Or, the content access client application may be responsiblefor decrypting content items, or at least maintaining DRM keys fordecrypting content items, so that another application on the device mayplay content. The client application may be a stand-alone application,such as a “mobile app,” that a user of the device may execute directly.Or, the client application may be a background process that conductsvarious activities such as described herein without directly interactingwith the user. As yet another example, the client application may be a“plug-in” or “extension” to another application, such as to a mediaplayer or web browser.

In an embodiment, a content access client application is also configuredto communicate with counterpart content server applications executing onlocal servers 150 via local connections. The content access clientapplication is more specifically configured to automatically locate acounterpart content server application (e.g. locate the IP addressand/or port of the content server application), and to stream ordownload selected local media content 154 via communications with thecontent server application.

The content server applications may, in an embodiment, be configured toonly send metadata 116 and/or media content 154 to the content accessclient applications. For instance, the content distributor may wish toensure that media content 154 is only available to devices 160 belongingto owners who have enrolled in a certain system or paid a subscriptionfee. The content access application may thus send certain credentials(e.g. a signature, key, login information, etc) to the content serverapplication. The content server application will only communicate with aclient application if these credentials are determined to be valid.However, in some embodiments, a client-side digital rights managementscheme may be deployed, and the content server application need notnecessarily take such precautions.

The content access application may further be responsible for generatingand presenting the interfaces described above, and/or for implementingvarious other functions of devices 160 described herein. Hence, byproviding computer code for executing the one or more clientapplications to devices 160, an operator of system 100 may therefore besaid to cause the devices 160 to perform the various device functionsdescribed herein.

2.6. Digital Rights Management

System 100 further comprises one or more digital rights managementserver components 180, also referred to herein as DRM servers 180. A DRMserver component 180 may, in an embodiment, be integrated into contentserver 110. In an embodiment, a DRM server 180 may instead be externalto content server 110. Generally, a DRM server 180 is responsible forproviding some digital rights information necessary for a device 160 toplay digitally-protected contents. The provided information may be, forinstance, keys (or portions thereof) for decrypting specific items ofcontent 114. Instead, or additionally, the provided information may be adevice-specific promotion code that enables a device 160 to execute asuitable client application for playing content items 154 downloaded tothe device 160. The promotion code may permit a device 160 to play anydownloaded content 154, or only items of content 154 matching certaincharacteristics, such as belonging to a certain subscription plan orhaving been downloaded from a specific local content server.

DRM servers 180 may be utilized to implement any suitable DRM scheme.For instance, in an embodiment, each content item may have a decryptionkey that must be used to decrypt the content before a device 160 canplay the content item. When downloading and/or before first playing thecontent item, the device 160 may be configured to send a message to aDRM server 180 requesting the decryption key. If the DRM server 180 canverify that the device 160 is allowed to play the content, the DRMserver 180 may send the decryption key to the device. As yet anotherexample, DRM keys are provided to local servers 150, which then relaythe decryption keys to each device 160 when the corresponding content isdownloaded. In an embodiment, the content decryption key isdevice-specific, such that the content decryption key can only beutilized by the receiving device 160. In an embodiment, the contentdecryption key is itself encrypted, and a device 160 must decrypt theencryption key using device-specific information such as a general orcontent-specific promotion code and/or an application signature.

In an embodiment, a content-specific partial key is stored on the localserver 150 with the associated content item 154. A master key for thespecific local server 150 or device 160 is distributed by the DRM server180. A device 160 may derive the rights information necessary to decrypta given content item 154 by combining the partial key of the givencontent item 154 with a suitable master key, in accordance with a DRMscheme described elsewhere in this application.

In an embodiment, a DRM server 180 is further capable of—or linked to abilling/payment server that is capable of—conducting transactions. Forinstance, a device 160 and/or local server 150 may be configured totransmit account identifier(s), such as a telephone number or a uniquedevice identifier, to the DRM server 180. The DRM server 180 may thenexamine the associated account and determine whether a payment is neededto access a requested content item or subscription. If so, then the DRMserver 180, or a backend payment server, may utilize payment informationassociated with the account or included with the message to conduct afinancial transaction. The DRM server 180 provides the necessary keys orcodes for the requested content or subscription only if the transactionwas successful. As another example, a retailer at which a local server150 is deployed may take payment for providing certain content to adevice locally (i.e. in the physical store). The retailer may then senda message to a DRM server (e.g. via the local server 150 or from aretail terminal) requesting an appropriate key or code. The message mayinclude an identifier for the retailer and an identifier for thepurchased content or subscription. The retailer may then be billed forhaving provided the content or subscription, and the appropriate key orcode may be returned to the retailer, who in turn provides it to theclient. In yet other embodiments, a separate billing server may beprovided for receiving records of content provided by a promotingentity, and for conducting billing based thereon.

In an embodiment, system 100 further includes an SMS gateway 170configured to send and receive Short Message Service (“SMS”) messages orother equivalent low-bandwidth messages over a network other than theInternet 190 (e.g. a cellular provider's network). The SMS gateway 170facilitates the transmission of information between DRM servers 180 anddevices 160 or local servers 150, without requiring that the devices 160and/or local servers 150 have access to the Internet 190. In anembodiment, a user can enter keys or codes transmitted by SMS to adevice 160 into suitable interface prompts in a client application or ata local server 150, thus allowing in essence two-way communicationbetween a DRM server 180 and a device 160 and/or a local server 150without access to the Internet. In an embodiment, some devices 160 maybe capable of intercepting SMS messages from a DRM server 180, such thata user need not manually re-enter a key or code transmitted over SMS.

In an embodiment, some or all of devices 160 and/or local servers 150may utilize a direct connection to Internet 190 for communicating withDRM servers 180, if available, since the transmissions are of relativelylow bandwidth and expense.

In an embodiment, system 100 includes both a DRM server component 180operated by the owner of the content server 110 as well as one or morethird-party DRM servers 180. The third-party DRM servers 180 aregenerally operated by providers or producers of specific items ofcontent 114, and responsible for providing the DRM licenses and/or keysnecessary to play their respectively provided contents. The DRM server180 operated by the owner of content server 110, meanwhile, isresponsible for relaying licenses or keys from the third-party DRMservers 180, and/or releasing device-specific promotion codes that allowthe devices 160 to use the client software.

2.7. Variations

System 100 illustrates only one of many possible arrangements ofcomponents configured to provide the functionality described herein.Other arrangements may include fewer, additional, or differentcomponents, and the division of work between the components may varydepending on the arrangement. For example, in some embodiments, contentpackaging tool 120, SMS gateway 170, and/or DRM server 180 may beomitted, along with any other components relied upon exclusively by theomitted component(s). As another example, in an embodiment, centralserver 110 is omitted and/or lacks the capability to send content toonline clients 130. In such an embodiment, a content packaging tool 120may generate content packages 124 directly from a data repository 112,without necessarily even being connected to the Internet 190.

In FIG. 1, the various components of system 100 are depicted as beingcommunicatively coupled to various other components by arrows. Thesearrows illustrate only certain examples of information flows between thecomponents of system 100. Neither the direction of the arrows nor thelack of arrow lines between certain components should be interpreted asindicating the existence or absence of communication between the certaincomponents themselves. Indeed, each component of system 100 may featurean open port, API, or other suitable communication interface by whichthe component may become communicatively coupled to other components ofsystem 100 as needed to accomplish any of the functions of system 100described herein.

3.0. Functional Overview

In an embodiment, the distribution of media content to devices havingminimal or no Internet connectivity is greatly simplified usingtechniques that involve distributing content to portable devices inpublic or semi-public areas via local connections to strategicallydeployed “offline” server devices. The processes described in thissection illustrate the various example techniques for accomplishing thisand other objectives.

The various elements of the described processes may be performed in avariety of systems, including systems such as system 100 describedabove. In an embodiment, each of the processes described in connectionwith the functional blocks described below may be implemented using oneor more computer programs, other software elements, and/or digital logicin any of a general-purpose computer or a special-purpose computer,while performing data retrieval, transformation, and storage operationsthat involve interacting with and transforming the physical state ofmemory of the computer.

3.1. Local Content Server Deployment

FIG. 2 illustrates an example process flow 200 for distributing contentto offline client devices, such as devices 160, according to anembodiment. At block 210, a content distributor, such as an operator ofcentral server 110 or of data repository 112, deploys (or causesdeployment of) local content servers, such as local servers 150, indifferent geographic locations. For instance, the content distributormay place the local content servers in stores, transportation hubs, orother strategic locations.

In an embodiment, the content distributor builds and/or assembles thelocal content servers using off-the-shelf computer hardware componentssuch as one or more processors, a motherboard, one or more hard drives,and various wired and/or wireless communication interfaces. The contentdistributor then installs custom server application software on localcontent servers. The server application software, when executed, isconfigured to cause the computer hardware components to perform thevarious local server functions described herein. In an embodiment, thecontent distributor may further package the local content servers indistinctive housing. For instance, a local content server may be encasedwithin a kiosk-like housing on which is depicted various advertisementsmeant to promote the content distributor's brand. The contentdistributor may then deploy the content servers at various strategiclocations, and/or send the content servers to other entities, such asstore owners, with instructions for deploying the content servers.

In an embodiment, the content distributor may contract with anotherentity to build and/or assemble the content servers. In an embodiment,pre-built computing devices such as tablets or portable devices may beused as local content servers. In an embodiment, the content distributormay send installation software to a promoting entity that allows thepromoting entity to install and execute the local server applicationsoftware on computing devices already owned by the promoting entity,such as on mobile phones.

3.2. Distribution of Content to Local Content Servers

At block 220, the content distributor generates one or more contentpackages, such as content packages 124, comprising digital media contentitems from a library of media contents, such as data repository 112. Thecontent packages will typically include only a subset of content itemsavailable in a library. The content packages may be generated based onany of a variety of considerations, such as release dates, preferencedata, ratings, geographic area, genre, promoting entity preferences,requests from specific customers at a location to which the contentpackage is to be sent, and so forth.

At block 230 the content distributor sends the one or more contentpackages to the local servers. The content distributor may send contentpackages using any of a variety of techniques, depending on theembodiment. For instance, content packages may be copied onto removablestorage media, such as USB drives, SD cards, swappable hard disks orsolid state disks, and so forth. The removable storage media may be sentby mail or otherwise physically transported to the locations at whichthe local content servers are deployed, with instructions to thepromoting entity for adding the content packages stored on the removablestorage media to the content servers. Once used, the removable storagemedia may optionally be returned to the content distributor for reuse.In an embodiment, service representatives may carry the removablestorage media from location to location and update the local contentservers for the promoting entities.

In an embodiment, blocks 220-230 are repeated on, for instance, aperiodic basis. For instance, a new content package may be mailed eachweek or each month. In an embodiment, the local content servers areinexpensive and/or portable, such that instead of sending removablestorage media to deployment locations, the content distributorperiodically sends entire local content server units to a promotingentity, pre-loaded with newly generated content packages. The promotingentity may optionally return the outdated local content server to thecontent distributor for re-use.

In certain embodiments, if certain local content servers have a reliableInternet connection, the content distributor may send content packagesto those local content servers directly over the Internet connection. Insome such embodiments, a local content server may specifically requestand receive individual content items directly from a central server,effectively forming its own custom content packages. For instance, if apromoting entity or customer connected to the local content serverindicates an interest in content not currently found on the localcontent server, the local content server may attempt to download thecontent in the background, as resources permit. The content may then bemade available for customers the next time the customers connect to thelocal content server.

At block 240, media content items and metadata from the content packagesare stored on one or more storage devices at each local content server.If content packages are distributed on removable media, a local contentserver may, in an embodiment, use the removable storage media as the oneor more storage devices instead of copying the content packages toanother storage device. In an embodiment, promoting entities and/orlocal content servers may optionally pick and choose which media contentitems to copy to the local content server, though in other embodimentsthe content packages may have already been generated based on selectionsby the promoting entity. In an embodiment, each local content server inan area or at a certain type of location (e.g. stores within a chain ofstores) may store the same media content items.

3.3. Device Provisioning

At block 250, portable devices are provisioned to access contentdistributed by the local content servers. In an embodiment, block 250 isonly performed the first time a portable device attempts to accesscontent at a local content server. The provisioning process may includesteps such as installing a content access client application from thecontent distributor on the device, collecting registration informationand sending the registration information to a central server, generatingan account to associate with the device, collecting payment, generatingor retrieving content access codes or other content rights information,and/or transferring an initial set of content items to the device.Depending on the embodiment, the provisioning process may compriseself-service and/or promoter-assisted steps. In an embodiment, block 280may be a substep of the provisioning process. In an embodiment, certaindevices may be pre-provisioned by a user or manufacturer without havingever attempted to connect to any local content server. Other aspects ofexample provisioning processes are described in other sections.

3.4. Offline Transfer to Portable Devices

Block 260 comprises establishing local connections between the portabledevices and the local content servers. For instance, a user of thedevice may direct the device to connect to a named network, such as awireless local area network or a Bluetooth personal area network. Such anetwork may be managed by a local content server, or by an externalwireless router. Or, the device may monitor for available networks andautomatically connect to the named network. Once connected, the device,or a content access client application installed thereon, mayautomatically attempt to contact the local content server at a common IPaddress or hostname that is assigned to the local content servers. Or,the device may monitor communications over the network for a messageannouncing the location of a local content server. In an embodiment, auser of a device may additionally or instead plug the device into a USBor other wired port of the local content server, thereby establishing adirect peer-to-peer connection. Peer-to-peer wireless connections mayalso be established, in certain embodiments.

At block 270, the local content servers transfer content to portabledevices. The transfers may occur in a variety of manners depending onthe embodiment. For instance, upon connecting to a local content server,a device may automatically be directed to download any and all contentavailable on the local content server that is not already stored on thedevice. For instance, a local server may store, at a given time, fivedifferent movies, which are updated on a periodic basis. Upon a newmovie replacing an old movie on the local server, devices that hadpreviously loaded the old movie will be updated to store the new moviethe next time the devices connect to the local server. Or, based on asubscription code supplied by the device, the local content server maydirect the device to download a specific subset of content to which thedevice is subscribed. Any suitable file transfer protocol may beutilized.

Block 270 may be repeated any time a device establishes a localconnection. Expired, viewed, and/or old content items on the device maybe removed to make room for new content items using variousprioritization schemes. Similarly, a variety of prioritization schemesmay be utilized to determine which contents to transfer to a device ifthe device lacks sufficient room to store all of the content identifiedfor the device.

In an embodiment, the local content servers may provide differentcontent versions to different types of devices according to devicecapabilities and/or device preferences. A content package may include anumber of different versions of the same content, encoded usingdifferent profiles. For instance, some profiles may provide higherresolutions and/or qualities at the costs of an increased storage sizeand higher processor utilization, whereas other profiles may providelower resolutions and/or profiles for devices with less resources and/orfor quick transfers if a user does not wish to wait for a higherresolution version. To this end, the local content server may beconfigured to detect device capabilities, and/or receive devicespecifications or user preferences directly from the device.

In an embodiment, the device may request specific content items from thecontent server. For example, the device may download, from a contentserver or from a central server, metadata describing available mediaitems on one or more of the content servers. The device may present aninterface displaying a menu of available content items in a contentaccess application. Using this interface, a user may select specificcontent items that the user wishes to automatically download from acontent server the next time the user is connected to one of the contentaccess servers that has the selected content items available. Similarinterfaces for allowing a user to select content items to download maybe presented on a centralized website, or using input/output componentsconnected directly to a local content server.

In an embodiment, to speed up transfer, or to allow content transferwhen other types of transfers are not possible, the local content servermay copy content items to a removable storage media, such as an SD card,that is insertable into the portable device. Typically, the content willthen remain on the removable storage media, and the device will play thecontent directly from the removable storage media. The removable storagemedia may be removable storage media already owned by the device owner,or the removable storage media may be sold to the user by the promotingentity. In an embodiment, the removable storage media may be soldpre-packaged by the content distributor or the promoting entity withcontent already stored thereon. In an embodiment, the removable storagemedia may be sold with an installer for the content access clientsoftware stored thereon. The removable storage media may optionally beconfigured to install the content access client software on the deviceautomatically. In an embodiment, the contents of such a removablestorage media may subsequently be replaced—potentiallyautomatically—upon the device establishing any of the above-describedtypes of local connections with any of the local content servers.

3.5. Rights Management and Payment

At block 280, digital rights data are provided to devices. The digitalrights information may be necessary for a device to play some or all ofmedia content distributed by the local content servers. In someembodiments, a device must also or instead send valid digital rightsinformation for a content item or for a subscription associated with thecontent item before a local content server will transmit the contentitem. The digital rights information may include, for instance,decryption keys for decrypting specific items of content, a key fordecrypting encrypted copies of the decryption keys, a license key forunlocking access to a content access client application, a promotioncode for unlocking a subscription to certain types of content, a masterkey for a local server or device, a partial content-specific decryptionkey, or any other suitable digital rights management data.

The digital rights information may be provided to a device in a varietyof manners. For example, when provisioning the device, a content accessapplication on the device may request a promotional code before allowinga user to launch the application and/or download content. The device mayrequest the promotional code from a digital rights management serverover an Internet connection or via SMS, using a unique identifier forthe device such as a phone number or hardware identifier. The digitalrights management server uses the supplied information to generate anappropriate promotional code. In an embodiment, the generatedpromotional code may also be specific to a subscription packagespecified in the request, or otherwise associated with the device, inthat it only allows the device to download and/or view content withinthe subscription package.

As another example, the device may prompt the user or a promoter toenter a promotional code. For instance, the content server or promotingentity may request a promotional code from the digital rights managementserver on behalf of the device, and display the promotional code so thatit may be entered on the user's device. In an embodiment, the localcontent server may request and transfer a promotional code directly tothe device. As yet another example, the device may be configured torequest a decryption key for specific content from a digital rightsmanagement server upon receiving the content and/or before playing thecontent.

In an embodiment, the digital rights management server may be configuredto provide digital rights information only upon verifying payment for asubscription package or specific content item associated with thedigital rights information. The digital rights management server may,for instance, conduct a transaction using payment information within therequest and/or within an account registered to the device during aprovisioning process. Or, the digital rights management server mayverify that the request includes a valid transaction identifier orsignature supplied by a promoting entity, indicating that payment hasalready been taken for the subscription package or specific contentitem.

In an embodiment, the digital rights information is time-limited. Forinstance, a subscription code may expire after a certain period of time,and block 280 must be repeated before the device can access contentagain.

Example DRM Schemes

Some example suitable digital rights management scheme involve splittingresponsibility for digital rights management key distribution betweenthe local servers and the DRM server. In embodiments that employ suchschemes, each local server stores a partial key for each item ofcontent. The partial key for a given item of content, taken alone, isinsufficient to decrypt the item of content. The partial key may havebeen provided to the local server, for instance, in metadata distributedto the local server with the content, or in metadata downloadedseparately by the local server from the central content server or theDRM server.

Meanwhile, the DRM server stores one or more master keys. In anembodiment, a separate master key exists for each local server. However,in other embodiments, there may be a separate master key for eachdevice, or a single master key that is associated with more than onelocal server. As with the partial key, the master key alone is likewiseinsufficient to decrypt any given item of content.

Each device is configured to receive the relevant master key from theDRM server during a device provisioning process. For instance, during aninitial registration process, an application distributed and installedby the operator of content server may be configured to request themaster key for a given local server directly from the DRM server. Uponvalidating certain information included in the application's request fora master key, such as a telephone number, user name, password, and/orany other suitable credentials, the DRM server may return the master keyto the application.

In some embodiments, the request for the master key and the master keymay be transmitted over a connection to the Internet or other wide areanetwork. In one such embodiment, this may be the only communication forwhich an Internet connection is required of a device, since the contentand relevant partial keys may be retrieved from a local content server.In some embodiments, even the request for the master key and the masterkey are not transmitted via an Internet connection at the device.Instead, the request and the master key may be transmitted using amessaging protocol such as binary SMS.

Whatever the communication mechanism, in some embodiments the master keymay be encrypted by the DRM server in such a manner that only theintended recipient device may decrypt it. For instance, the DRM servermay encrypt the master key using a device-specific identifier that issupplied to the DRM server by the device during a provisioning process.The device then uses this identifier to decrypt the master key asneeded.

In an embodiment, the device is configured to automatically receive andstore the master key without the involvement of a user. In otherembodiments, the device may prompt the user to input the master key, oran encrypted form of the master key, manually via any suitable userinterface. In such embodiments, the master key may be requested byand/or returned to an entirely different device.

In an embodiment, a local server may serve as a proxy by which themaster key is retrieved for a given device. For instance, the localserver may receive device-specific credentials for a given device,either from the device directly, or entered by a user or a promotingentity. The local server may then request the master key using thecredentials, and supply the returned master key (or encrypted masterkey) to the device.

Each device is configured to also receive the partial key for a givencontent item from the local server. For instance, the local server mayinclude the partial key in metadata found in a file, directory, ordatabase record that stores or is otherwise associated with the contentitem. An operator-installed application on the device may be configuredto download the partial key or the entire metadata automatically whendownloading a given item of content. In some embodiments, a device maybe configured to download the partial key or the entire metadata, beforeeven requesting the content, or after receiving the content.

Each device is configured to generate a content-specific key for a givenitem of content by executing a particular algorithm that is a functionof the master key of the local server from which the content isdownloaded, and the partial key of the given content item. For example,the content-specific key may be the partial key combined with the masterkey. The device may store the content-specific key locally for use indecrypting the given content item. The content-specific key may, in someembodiments, be stored in a secure form, such that it may only beaccessed and/or decrypted by the device.

In an embodiment, the master key returned to the device may encodeinformation indicating various criteria relevant to the device, such asa subscription level of the device, a time period during which thesubscription level is valid, and/or other suitable criteria. Hence,different master keys may be exist for different subscription levels ortime periods. The algorithm employed by the application to generatecontent-specific keys will only work with a given master key if thecriteria encoded in the master key apply to the context in which thecontent-specific key is being generated. For instance, if a content itemis not viewable without a certain subscription, and the master keystored at a device does not indicate that such a subscription iscurrently associated with the device, the device may fail to generate avalid content-specific key. A device may further retrieve updated masterkeys that reflect changing criteria (e.g. a new subscription) as needed.

In an embodiment, a content-specific key may also encode such criteria,and the device may be configured to validate the criteria before playingthe content. In another embodiment, no constraints are imposed on acontent-specific key, once generated. In embodiments, a device insteadutilizes other techniques outside of the key-generation process toenforce various criteria such as the existence of a valid subscription.

In an embodiment, when connecting to a local server for the first time,a device must retrieve the master key for that local server from the DRMserver, even if the device already has a master key for another localserver. Hence, a device may have multiple master keys for differentlocal servers. In an embodiment, master keys may be retrieved formultiple local servers during a provisioning process. For instance,during the provisioning process a device may receive all of the masterkeys for local servers in a certain geographic area. In an embodiment,each time a device connects to a local server, the device checks to seeif the device has a master key for that local server. If not, the deviceretrieves a suitable master key, or prompts the user to begin aprovisioning or registration process so that a suitable master key maybe obtained.

In an embodiment, the master key for a local server need not be obtainedbefore downloading content from the local server, but rather need onlybe obtained some time before the content is viewed.

The above described DRM scheme is provided for illustrative purposes.However, any other suitable DRM scheme may instead be utilized whenpracticing the described techniques.

3.6. Miscellaneous

Returning to FIG. 2, at block 290, based on verifying that respectivelyreceived digital rights information authorizes the portable mediadevices to play certain items of media content, the portable mediadevices play the content using any suitable content playback techniques.Note that flow 200 may be completed without the portable devices or eventhe local content servers connecting to the Internet, thus achieving anoffline distribution and playback of content.

Flow 200 is one example of a technique for content distribution usingthe described systems. Other techniques may involve fewer or additionalelements in varying arrangements. For instance, in an embodiment, block250 may be omitted for devices that are pre-provisioned via a wirelessservice provider or manufacturer. As another example, block 280 may beomitted in systems without rights management or with different types ofrights management schemes.

Example Offline Content Selection

In an embodiment, metadata describing available content items isdownloaded to a portable device when the portable device accesses afirst local content server and/or when the portable device accesses acontent distributor website. Subsequently, while not connected to anylocal content server, a user may view the metadata by, for example,opening a content access client application on the device. The user mayselect content of interest while viewing this metadata. The devicestores the selections. The device may optionally indicate, based on themetadata, geographic locations of local content servers to which theuser may connect to download the selected content.

Subsequently, the device may detect and initiate a local connection toan available network, such as a connection to a certain wirelessnetwork. The application detects the presence of a second local contentserver, which may not necessarily be the same as the first local contentserver. The application automatically identifies, based on the storedselections and metadata from the second local content server, a selectedcontent item that may be downloaded from the second local contentserver. Without necessarily being further prompted by the user, theapplication automatically downloads the content. The device notifies theuser when the content has been downloaded.

Optionally, before allowing the user to select the content, or beforedownloading the content, the device can verify whether the device isactually allowed to play the content. If the device is not allowed toplay the content, the device may ask the user to agree to pay for thecontent, should the device download the content. Or, the device may goahead and download the content, but ask the user to pay for the contentbefore allowing the user to view the content. Payment may be conductedover the Internet, via SMS, and/or with the assistance of promoter, asdescribed in other sections.

Device-to-Device Sharing

According to an embodiment, another technique for distributing metadataand/or content items with portable media devices is for portable devicesthat have downloaded content from a local content server to share thatcontent with other portable media devices that have been provisioned foraccess to the local content servers. For instance, two users ofprovisioned devices may meet each other on a subway or at a park or atany other suitable location. The users may activate the contentdistributor's content access application on their respective devices.The application instances may detect each other and, if approved by theusers, initiate a transfer of metadata and/or content items, dependingon the embodiment. The transfer may occur using any suitablepeer-to-peer sharing technique.

If only metadata is transferred, the receiving device's application mayanalyze the metadata to determine if new content is available at anoffline content server. If new content is available, and optionally ifthe metadata matches certain characteristics pre-defined by the user ofthe device, the device may optionally notify the user of theavailability of the new content, which the user may then select fordownload using techniques such as described above. Otherwise, theapplication may simply update its metadata and use the updated metadatato present more up-to-date information to the user at a later time whenthe user requests such information. Meanwhile, if actual content itemsare to be transferred, the devices may search each other's inventoriesfor content items of interest. When a content item of interest is found,the content item may be downloaded from the other device.

In some embodiments, the transfer of metadata and/or content items maybe automatic, in that a user need not necessarily instruct the device toinitiate the transfer. In some embodiments, the application isconfigured to run constantly in the background, and locate otherprovisioned devices automatically. Hence, for example, a user might besitting on a subway while her device searches in the background forcontent of interest on devices owned by other passengers. By the timethe user is done riding the subway, the device may notify the user thatthe device downloaded, for instance, three additional movies during thesubway ride. In an embodiment, a user may be required to opt-in to sucha feature, on account of privacy concerns and/or concerns about devicebattery life.

Seamless Switching Between Local Servers and a Central Server

In an embodiment, a client device within the described systems mayaccess content and metadata both on local servers and on the centralserver, depending on the network connectivity of the device. When anitem of content is available on both the central server and a localserver, the device is configured to provide a seamless transition fromutilizing the central server to utilizing the local server, and viceversa, as the device transitions between local connections and wide areanetwork (e.g. Internet) connections. Thus, for example, a user may makecontent selections based on metadata provided by the central server overan Internet connection, and then receive the selected content when thedevice has a local connection to a local server.

In an embodiment, content access application software on the device isconfigured to manage download processes so as to permit partialdownloads. A download process for a content item may begin, forinstance, at one time with one local content server. The downloadprocess may be interrupted when the user takes the device away from thelocal content server before the download has concluded. The applicationmay then resume the download when the device is again connected to alocal content server, which need not be the same local content serverthat the download process began at.

Moreover, a download process may begin with an online connection to acentral server over the Internet, be interrupted when Internetconnectivity is lost, and conclude when the device connects to a localcontent server. Similarly, a download process may begin when the deviceconnects to a local content server, be interrupted when the deviceleaves the vicinity of the local content server, and resume when thedevice is connected to the central server over the Internet.

Content Transfer Optimizations

In an embodiment, a content access application may show a progressscreen comprising estimated time(s) remaining for downloading certaincontent items. Any suitable estimation technique may be used, but in atleast one embodiment, the local content server may compute the estimatebased on factors such as a current number of connections, an averagetransfer speed, a file size, and so forth. The application may also orinstead generate a visual or audible notification when the user hasleft, or is close to leaving, the proximity of the local contentserver's wireless access point without having completed a downloadprocess. If the user wishes to finish the download, the user may thuschoose to remain in the proximity until the download is complete. In anembodiment, the progress screen includes interface controls that allowthe user to instruct the device to perform tasks such as stoppingdownloads of certain items, reprioritizing a download queue, downloadingalternative (e.g. larger or smaller) versions of selected content items,viewing associated metadata, and so forth.

In an embodiment, instead of downloading content automatically when alocal content server is available, a device may simply notify the useraudibly and/or visually that certain content is available. The user maythen select which content to download.

In an embodiment, a local content server is configured to automaticallyadjust various operating parameters to meet various quality of servicemetrics. For instance, the local content server may limit the number ofactive connections or downloads so as to ensure that active downloadsare completed within a certain period of time. The local content servermay prioritize certain types of operations, such as provisioningoperations. The local content server may also or instead suggest tovarious users alternative connection mechanisms, such as USBconnections, by which the users may speed up the download process inheavy usage situations. In an embodiment, certain classes of devices orusers may be prioritized. For instance, a gold subscription may allow adevice to always receive higher bandwidth downloads than a silversubscription.

Device-to-Local Server Content Sharing

In an embodiment, when a device connects to a local server, the devicemay share with the local server an inventory of content on the device.The inventory may include content that has been downloaded from thelocal server itself, from another local server, from the central server,and/or from any other suitable source within a content distributionsystem. The local server may compare the inventory to its own inventory.If the device's inventory includes content not found on the localserver, the local server may request the content from the device.Depending on the embodiment and/or user preferences, the device maybegin transferring the requested content immediately, wait to transferthe requested content until the device has downloaded other content fromthe local server, and/or request permission from a user of the device tobegin transferring content to the local server.

In an embodiment, the user of device may be offered an incentive forsharing the content with the local server, such as a free content itemfrom the local server's inventory, a credit to the user's account, anextension of the user's subscription, an unlock code for a specific itemof content, or any other suitable incentive.

Advertisements

In an embodiment, in addition to downloading content from a localserver, a device may also be configured to download advertisements fromthe local server, such as trailers for other items of content, banneradvertisements, video commercials, and so forth. Advertisements may bedistributed to the local server with content packages, by a connectionto an advertisement server, or via any other suitable mechanism. Forexample, content trailers may be found in the metadata for a contentitem. Or, content trailers may be generated dynamically by, forinstance, the local server extracting a short video clip from therelevant content item. Using a DRM mechanism such as the split keymechanism described above, the local server may be able to extract atrailer from a content item even if the local server is not itself ableto decrypt the item (or the trailer).

The device may be configured to display the advertisements at any of avariety of times. For instance, before sending content to a device, alocal server may send a set of trailers that the user of the device maywatch while the content is downloading. Or, the device may be configuredto play an advertisement before, after, or during presentation of acontent item downloaded from the local server.

In an embodiment, the advertisements may customized based on userpreferences and/or prior interactions between the device and the localserver. The local server gathers group-based and/or device-specificanalytics. For instance, the local server may track which content itemshave been downloaded most frequently or by a given device. As anotherexample, an application may report to the local server which contentswere played by the device, either fully or partially. The local servermay, based on the analytics and on metadata associated with theadvertisements, select a set of advertisements deemed most relevant tothe user of the device, and send those advertisements to the device. Asanother example, the local server may send a content trailer for each ofthe most popular content downloads from the local server, or for eachnew content item at the local server.

In an embodiment, a local server may further receive analytics gatheredby other local servers and/or the central server. The analytics may beshared directly over the Internet, or distributed with content packages.The shared analytics may also be used for personalized targeting ofadvertisements. Additionally, or instead, the analytics may be utilizedfor a variety of other purposes known within the art.

4.0. Example Embodiments

Example embodiments are represented in the following numbered clauses:

1. A system comprising: application software, resident on portable mediaplayback devices, configured to play media content items; one or morelocal content servers, each local server of the one or more localcontent servers comprising: one or more storage devices storing localcopies of the media content items; one or more communications interfacesconfigured to establish local connections between the local server andmultiple media playback devices, of the portable media playback devices,that are within a certain proximity to the local server; logic,implemented at least partially by hardware at the local server,configured to cause the local server to send, over the localconnections, copies of the media content items stored on the one or morestorage devices to the multiple media playback devices when the localconnections are established.

2. The system of Clause 1, wherein at least a first local server of theone or more local content servers is not connected to the Internet andis not connected to any other local content server.

3. The system of Clause 1, further comprising: a central data repositorystoring a superset of media content, including at least the mediacontent items; a central server coupled to a wide area network, thecentral server configured to send copies of the media content itemsstored in the central data repository over the wide area network tocertain media playback devices of the portable media playback devices,the wide area network not including any of the local connections betweenthe one or more local content servers and the multiple media playbackdevices.

4. The system of Clause 1, further comprising: a central data repositorystoring a superset of media content, including at least the mediacontent items; a content packaging component configured to generatecontent packages based on the superset of media content; wherein the oneor more local content servers are configured to store the local copiesof the media content items in response to receiving the content packagesby one or more: receiving the content packages over a wide area network,or reading the content packages from a removable storage device.

5. The system of Clause 1, wherein at least a first local server of theone or more local content servers is configured to direct a givenportable device to an installer file for the application softwareresponsive to the given portable device establishing an initialconnection to the first local server.

6. The system of Clause 1, wherein, upon a given device of the portablemedia playback devices establishing at least certain types connections,the application software on the portable device is configured to: send amessage to a common address assigned to each local server of the one ormore local content servers, and, when one of the local content serversis contactable via the common address, automatically download one ormore content items or content metadata from the contacted local server.

7. The system of Clause 1, further comprising: a digital rightsmanagement server, separate from the local server, configured togenerate rights information necessary for the application software toplay certain content of the media content items on a given device;wherein the application software is configured to perform one or moreof: requesting the rights information from the digital rights managementserver, or prompting a user to input the rights information; wherein theapplication software is further configured to determine whether a deviceis authorized to play certain content of the media content items basedon reading the rights information.

8. The system of Clause 1, further comprising: a digital rightsmanagement server, separate from the local server, configured togenerate rights information necessary for the application software toplay certain content of the media content items on a given device; aShort Message Service (“SMS”) gateway configured to relay SMS-basedmessages carrying the rights information from the digital rightsmanagement server to one or both of: the one or more local contentservers or the portable media playback devices; wherein the applicationsoftware is further configured to determine whether a device isauthorized to play certain content of the media content items based onreading the rights information.

9. The system of Clause 1, wherein the application software is furtherconfigured to: present a menu of available content based on metadatafrom the one or more local content servers, receive input selectingcontent of interest from the menu when no connection to any of the oneor more local content servers is available, and automatically downloadthe content of interest upon detecting a connection to one of the one ormore local content servers.

10. The system of Clause 1, wherein each of the local connections is oneof an 802.11 wireless-based connection, Bluetooth connection, orUniversal Serial Bus connection, wherein the media content items includedigital movie files, wherein at least two or more of the multiple mediaplayback devices are connected to a given local server concurrently.

11. A method comprising: based on a library of media content, a contentdistributor periodically generating one or more content packagescomprising digital media content items from the library; storing the oneor more content packages on one or more local media servers deployed ata plurality of different geographic locations, the one or more localmedia servers operated by promoting entities other than the contentdistributor; causing installation of, on the one or more local mediaservers, server application software comprising instructions that, whenexecuted by the one or more local media servers, cause the one or morelocal media servers to send digital media content items from the one ormore content packages to portable media playback devices that establishlocal connections to the one or more local media servers, the localconnections being local area network connections or wired connections,the portable media playback devices executing client applicationsoftware code generated by the content distributor, the clientapplication software configured to allow the portable media playbackdevices to play the digital media content items only upon input ofrights information; receiving, at a digital rights management serveroperated by the content distributor, requests for rights information toaccess the digital media content items; sending the rights informationin response to the requests.

12. The method of Clause 11, wherein the requests for rights informationare received via a Short Message Server (“SMS”) gateway.

13. The method of Clause 11, further comprising: the content distributorperiodically updating the one or more content packages to include newmedia content items; the content distributor periodically deliveringupdated storage devices comprising the updated one or more contentpackages to the promoting entities; storing the updated one or morecontent packages on the one or more local media servers; wherein theinstructions of the server application software are configured to, basedon the updated one or more content packages, cause a given local mediaserver to automatically send a new content item to which a given deviceis subscribed responsive to the given device reconnecting to the givenlocal media server.

14. The method of Clause 11, further comprising: the content distributorbilling one of a promoting entity or an owner of a portable device inresponse to a request for the rights information.

15. The method of Clause 11, further comprising: copying at least afirst content package of the one or more content packages to removablestorage media; copying an installer for the client application softwarecode to the removable storage media; distributing the removable mediadrive to promoting entities for sale to users of the portable mediaplayback devices, the portable media playback devices configured toexecute the installer on the removable storage media to install theclient application software code, the client application software codeconfigured to play media content items in the first content packagestored on the removable storage media, the one or more local mediaservers configured to send new content items to replace media contentitems in the first content package.

16. One or more non-transitory computer-readable media storinginstructions that, when executed by one or more computing devices,cause: storing, at a plurality of local media servers, media contentcollections; establishing local connections between particular localservers of the local media servers and particular mobile devices of aplurality of mobile devices, the local connections being one or both of:local area network connections, or peer-to-peer connections; receiving,at a central digital rights management server, requests to unlock accessfor the particular mobile devices to content items in the media contentcollections; sending, from the central digital rights management server,responses comprising rights information for the particular mobiledevices to unlock access to the content items; transmitting the contentitems from the particular local servers to the particular mobile devicesover the local connections, the mobile devices configured to utilize therights information to determine whether the mobile devices are permittedto play the particular content items.

17. The one or more non-transitory computer-readable media of Clause 16,wherein the requests to the central digital rights management server andthe responses from the central digital rights management server are sentvia SMS messages.

18. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by the one or more computingdevices, further cause: a particular mobile device establishing a firstconnection to a first local server of the plurality of local mediaservers; the first local server directing the particular mobile deviceto install a content access application; the content access applicationcausing the particular mobile device to download at least first contentitems of the particular content items from the first local server; theparticular mobile device subsequently establishing a second connectionto a second local server of the plurality of local media servers; upondetecting the second connection, the content access applicationautomatically causing the particular mobile device to download at leastsecond content items of the particular content items from the secondlocal server.

19. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by the one or more computingdevices, further cause: a first mobile device establishing a firstconnection to a first local server of the plurality of local mediaservers; the first mobile device downloading, through a content accessapplication installed on the first mobile device, metadata describing acatalog of content items available at the first local server; the firstmobile device detecting a second mobile device on which the contentaccess application is installed; responsive to detecting the secondmobile device, the first mobile device sharing the metadata describingthe catalog to the second mobile device; based on the metadata receivedfrom the first mobile device, the second mobile device displayinginformation about one or more content items that are newly available atone or more of the local media servers.

20. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by the one or more computingdevices, further cause: a first mobile device establishing a firstconnection to a first local server of the plurality of local mediaservers; the first mobile device downloading, through a content accessapplication installed on the first mobile device, first content storedat the first local server; the first mobile device detecting a secondmobile device on which the content access application is installed;responsive to detecting the second mobile device, the first mobiledevice sharing the first content with the second mobile device; thesecond mobile device playing the first content responsive to readingrights information data from the digital rights management serverindicating that the second mobile device is permitted to play the firstcontent.

21. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by one or more computingdevices, further cause: sending, from the local media servers to theparticular mobile devices, partial content-specific decryption keys forthe content items; wherein the rights information sent by the centraldigital rights management server includes master keys that are specificto one or more of the local media servers; generating, at the particularmobile devices, based on the partial content-specific decryption keysand the master keys, content-specific decryption keys for decryptingspecific items of the content items.

22. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by one or more computingdevices, further cause: identifying, by a given device of the pluralityof mobile devices, a media profile that is preferred for media playbackat the given device; based on the identified media profile, selecting,by the given device, a specific version of a given content item fordownload from a given local server.

23. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by one or more computingdevices, further cause: a given device establishing a wide area networkconnection with a central media server; the given device downloadingmetadata describing a catalog of content from the central media server;the given device receiving user input selecting a specific item ofcontent in the catalog for download; the given device downloading atleast a portion of the specific item over a local connection from one ofthe local media servers, instead of from the central media server.

24. The one or more non-transitory computer-readable media of Clause 16,wherein the instructions, when executed by one or more computingdevices, further cause: a given device downloading a first portion of aspecific item of content over a local connection with a local mediaserver; the given device downloading a second portion of the specificitem over a wide area network connection with a central media server.

5.0. Implementation Mechanism Hardware Overview

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 3 is a block diagram that illustrates a computersystem 300 upon which an embodiment of the invention may be implemented.Computer system 300 includes a bus 302 or other communication mechanismfor communicating information, and a hardware processor 304 coupled withbus 302 for processing information. Hardware processor 304 may be, forexample, a general purpose microprocessor.

Computer system 300 also includes a main memory 306, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 302for storing information and instructions to be executed by processor304. Main memory 306 also may be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 304. Such instructions, when stored innon-transitory storage media accessible to processor 304, rendercomputer system 300 into a special-purpose machine that is customized toperform the operations specified in the instructions.

Computer system 300 further includes a read only memory (ROM) 308 orother static storage device coupled to bus 302 for storing staticinformation and instructions for processor 304. A storage device 310,such as a magnetic disk or optical disk, is provided and coupled to bus302 for storing information and instructions.

Computer system 300 may be coupled via bus 302 to a display 312, such asa cathode ray tube (CRT), for displaying information to a computer user.An input device 314, including alphanumeric and other keys, is coupledto bus 302 for communicating information and command selections toprocessor 304. Another type of user input device is cursor control 316,such as a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 304 and forcontrolling cursor movement on display 312. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

Computer system 300 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 300 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 300 in response to processor 304 executing one or more sequencesof one or more instructions contained in main memory 306. Suchinstructions may be read into main memory 306 from another storagemedium, such as storage device 310. Execution of the sequences ofinstructions contained in main memory 306 causes processor 304 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperation in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical or magnetic disks, such as storage device 310.Volatile media includes dynamic memory, such as main memory 306. Commonforms of storage media include, for example, a floppy disk, a flexibledisk, hard disk, solid state drive, magnetic tape, or any other magneticdata storage medium, a CD-ROM, any other optical data storage medium,any physical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 302. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 304 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 300 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 302. Bus 302 carries the data tomain memory 306, from which processor 304 retrieves and executes theinstructions. The instructions received by main memory 306 mayoptionally be stored on storage device 310 either before or afterexecution by processor 304.

Computer system 300 also includes a communication interface 318 coupledto bus 302. Communication interface 318 provides a two-way datacommunication coupling to a network link 320 that is connected to alocal network 322. For example, communication interface 318 may be anintegrated services digital network (ISDN) card, cable modem, satellitemodem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, communicationinterface 318 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN. Wireless links may also beimplemented. In any such implementation, communication interface 318sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

Network link 320 typically provides data communication through one ormore networks to other data devices. For example, network link 320 mayprovide a connection through local network 322 to a host computer 324 orto data equipment operated by an Internet Service Provider (ISP) 326.ISP 326 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 328. Local network 322 and Internet 328 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 320and through communication interface 318, which carry the digital data toand from computer system 300, are example forms of transmission media.

Computer system 300 can send messages and receive data, includingprogram code, through the network(s), network link 320 and communicationinterface 318. In the Internet example, a server 330 might transmit arequested code for an application program through Internet 328, ISP 326,local network 322 and communication interface 318.

The received code may be executed by processor 304 as it is received,and/or stored in storage device 310, or other non-volatile storage forlater execution.

In an embodiment, some or all of the systems described herein may be orcomprise server computer systems, including one or more server computerdevices that collectively implement various components of the system asa set of server-side processes. The server computer systems may includeweb server, application server, database server, and/or otherconventional server components that the depicted components utilize toprovide the described functionality. The server computer systems mayreceive network-based communications comprising input data from any of avariety of sources, including without limitation user-operated clientcomputing devices such as desktop computers, tablets, or smartphones,remote sensing devices, and/or other server computer systems.

In an embodiment, certain server components may be implemented in fullor in part using “cloud”-based components that are coupled to thesystems by one or more networks, such as the Internet. The cloud-basedcomponents may expose interfaces by which they provide processing,storage, software, and/or other resources to other components of thesystems. In an embodiment, the cloud-based components may be implementedby third third-party entities, on behalf of another entity for whom thecomponents are deployed. In other embodiments, however, the describedsystems may be implemented entirely by computer systems owned andoperated by a single entity.

6.0. Extensions and Alternatives

As used herein, the terms “first,” “second,” “certain,” and “particular”are used as naming conventions to distinguish queries, plans,representations, steps, objects, devices, or other items from eachother, so that these items may be referenced after they have beenintroduced. Unless otherwise specified herein, the use of these termsdoes not imply an ordering, timing, or any other characteristic of thereferenced items.

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. Thus, the sole and exclusive indicatorof what is the invention, and is intended by the applicants to be theinvention, is the set of claims that issue from this application, in thespecific form in which such claims issue, including any subsequentcorrection. In this regard, although specific claim dependencies are setout in the claims of this application, it is to be noted that thefeatures of the dependent claims of this application may be combined asappropriate with the features of other dependent claims and with thefeatures of the independent claims of this application, and not merelyaccording to the specific dependencies recited in the set of claims

Any definitions expressly set forth herein for terms contained in suchclaims shall govern the meaning of such terms as used in the claims.Hence, no limitation, element, property, feature, advantage or attributethat is not expressly recited in a claim should limit the scope of suchclaim in any way. The specification and drawings are, accordingly, to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A system comprising: a central media serverconfigured to send copies of media content items from the central mediaserver over a wide area network to certain media playback devices of aplurality of mobile devices; at least one local media server, separatefrom the central media server, configured to: store copies of at least asubset of the media content items; establish local connections withparticular mobile devices of the plurality of mobile devices; responsiveto requests for particular content items of the media content items,transmit copies of the particular content items to the particular mobiledevices over the local connections; upon establishment of a first localconnection with a first mobile device of the particular mobile devices,request that the first mobile device transfer a first content item, ofthe media content items, which is stored at the first mobile device, tothe local media server; store a first copy of the first content item atthe local media server when received from the first mobile device. 2.The system of claim 1, further comprising: a second local media server,separate from the central media server, configured to transfer a copy ofthe first media content item to the first mobile device.
 3. The systemof claim 1, wherein the local media server is further configured to sendat least partial rights information to a second mobile device, of theparticular mobile devices, that receives the first content item from thelocal media server, the second mobile device configured to utilize therights information to determine whether the second mobile device ispermitted to play the first content item.
 4. The system of claim 1,wherein the local media server is further configured to: direct a givenmobile device to an installer file for content access applicationsoftware responsive to the given mobile device establishing an initialconnection to the local media server, the content access applicationincluding first instructions that, when executed by the first mobiledevice, cause the first mobile device to transfer the first copy of thefirst content item to the local media server responsive to the firstcontent item being requested, the content access application furtherincluding second instructions that, when executed by a second mobiledevice, cause the second mobile device to request the first content itemfrom the local media server.
 5. One or more non-transitorycomputer-readable media storing instructions that, when executed by oneor more computing devices, cause performance of: detecting a first localconnection between a local content server and a first mobile device;requesting transfer of a first copy of a particular content item fromthe first mobile device to the local content server; responsive to therequesting, receiving the first copy of the particular content item atthe local content server from the first mobile device over the localconnection; storing the first copy of the particular content item at thelocal content server; detecting a second local connection between thelocal content server and a second mobile device; transferring a secondcopy of the particular content item from the local content server to thesecond mobile device over the second local connection.
 6. The one ormore non-transitory computer-readable media of claim 5, wherein theinstructions, when executed by the one or more computing devices,further cause performance of: comparing first inventory data identifyingone or more content items stored on the media device to a localinventory of content stored at the local content server; determining,based on the comparing, that the one or more content items include atleast one item not stored at the local content server; requestingtransfer of the first copy responsive to the determining.
 7. The one ormore non-transitory computer-readable media of claim 6, wherein thefirst mobile device is configured to automatically send the inventorydata to the local content server responsive to establishment of thefirst local connection.
 8. The one or more non-transitorycomputer-readable media of claim 5, wherein the first mobile device isconfigured to automatically transfer the first copy of the particularcontent item responsive to the requesting, without requesting permissionfrom a user of the first mobile device.
 9. The one or morenon-transitory computer-readable media of claim 5, wherein theinstructions, when executed by the one or more computing devices,further cause performance of: sending a copy of a first content item tothe first mobile device over the first local connection, the localcontent server waiting to request the particular content item untilcompletion of sending the copy of the first content item.
 10. The one ormore non-transitory computer-readable media of claim 5, wherein theinstructions, when executed by the one or more computing devices,further cause performance of, responsive to receiving the particularcontent item over the first local connection, performing one or more of:sending a first content item to the first mobile device, sending rightsdata for the first content item to the first mobile device, or updatingaccount data for a user of the first mobile device.
 11. The one or morenon-transitory computer-readable media of claim 5, wherein theinstructions, when executed by the one or more computing devices,further cause performance of: receiving, at a digital rights managementserver, requests to unlock access for the second mobile device to theparticular content item; sending, from the digital rights managementserver, rights information for the second mobile device to unlock accessto the particular content item, the second mobile device configured toutilize the rights information to determine whether the second mobiledevice is permitted to play the particular content item.
 12. The one ormore non-transitory computer-readable media of claim 11, wherein theinstructions, when executed by the one or more computing devices,further cause performance of: sending, from the local content server tothe second mobile device, a partial decryption key; generating, at thesecond mobile device, based on the partial decryption keys and therights information, a decryption key for decrypting the particularcontent item.
 13. The one or more non-transitory computer-readable mediaof claim 5, wherein the local content server is a first local contentserver, and the first mobile device received the particular content itemfrom a second local content server that is not connected to the firstlocal content server.
 14. The one or more non-transitorycomputer-readable media of claim 5, wherein the instructions, whenexecuted by one or more computing devices, further cause performance of:directing a given mobile device to an installer file for content accessapplication software responsive to the given mobile device establishingan initial connection to the local content server, the given mobiledevice including at least one or the first mobile device and the secondmobile device, the content access application including firstinstructions that, when executed by the first mobile device, cause thefirst mobile device to transfer the first copy of particular contentitem to the local content server responsive to the requesting, thecontent access application further including second instructions that,when executed by the second mobile device, cause the second mobiledevice to request the particular content item from the local contentserver.
 15. The one or more non-transitory computer-readable media ofclaim 5, wherein each of the first local connection and the second localconnection is one of an 802.15 wireless-based connection, Bluetoothconnection, or Universal Serial Bus connection.
 16. The one or morenon-transitory computer-readable media of claim 5, wherein theinstructions, when executed by one or more computing devices, furthercause performance of: responsive to detecting the second localconnection, sending inventory data to the second mobile deviceindicating that the particular content item is available for download bythe second mobile device.
 17. A method comprising: detecting a firstlocal connection between a local content server and a first mobiledevice; requesting transfer of a first copy of a particular content itemfrom the first mobile device to the local content server; responsive tothe requesting, receiving the first copy of the particular content itemat the local content server from the first mobile device over the localconnection; storing the first copy of the particular content item at thelocal content server; detecting a second local connection between thelocal content server and a second mobile device; transferring a secondcopy of the particular content item from the local content server to thesecond mobile device over the second local connection.
 18. The method ofclaim 17, further comprising: receiving, at a digital rights managementserver, requests to unlock access for the second mobile device to theparticular content item; sending, from the digital rights managementserver, rights information for the second mobile device to unlock accessto the particular content item, the second mobile device configured toutilize the rights information to determine whether the second mobiledevice is permitted to play the particular content item.
 19. The methodof claim 17, further comprising: responsive to receiving the particularcontent item over the first local connection, performing one or more of:sending a first content item to the first mobile device, sending rightsdata for the first content item to the first mobile device, or updatingaccount data for a user of the first mobile device.
 20. The method ofclaim 17, further comprising: directing a given mobile device to aninstaller file for content access application software responsive to thegiven mobile device establishing an initial connection to the localcontent server, the given mobile device including at least one or thefirst mobile device and the second mobile device, the content accessapplication including first instructions that, when executed by thefirst mobile device, cause the first mobile device to transfer the firstcopy of particular content item to the local content server responsiveto the requesting, the content access application further includingsecond instructions that, when executed by the second mobile device,cause the second mobile device to request the particular content itemfrom the local content server.